fix: fail early when Git Bash is missing - #430
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: dee8790 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…sh-prereq # Conflicts: # packages/agent-core/src/rpc/core-api.ts
commit: |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
No linked issue. This fixes a Windows startup failure path found while testing the Git Bash prerequisite.
Problem
On Windows, Kimi Code requires Git Bash. Before this change, CLI startup did not explicitly await the local runtime environment probe, so a missing Git Bash install could fail later instead of exiting cleanly at startup.
What changed
Added a core runtime environment check, exposed it through the SDK harness, and call it from both shell and print CLI startup before config/session initialization continues. Session creation and resume now use the same lazy Kaos initializer, and tests cover early short-circuiting in both startup modes.
Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.